You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Session creation times show significant variance between iterations, ranging from 4.55s to 51.12s, which could indicate potential performance issues in the autoscaling system.
Initial session creation failures should be eliminated to ensure reliable system startup
The initial session creation failures in iteration 1 should be investigated and addressed. Having 2 failed sessions at startup could indicate configuration or resource availability issues.
Why: The suggestion identifies a critical startup reliability issue where initial session creation is failing, which could impact system availability and user experience.
8
System startup reliability needs improvement to prevent initial session creation failures
Initial iteration shows 3 failed session creations, indicating potential startup issues that need investigation and fixing.
Why: The suggestion highlights a significant reliability issue where all three initial session creations are failing, indicating a potential systemic startup problem.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
User description
This PR contains the results of the autoscaling tests in Kubernetes
PR Type
Tests
Description
Updated Kubernetes autoscaling test results across multiple scenarios.
Adjusted metrics for deployment count, job count, and chaos scenarios.
Enhanced test data to reflect new scaling behaviors and session handling.
Improved consistency and accuracy in test result documentation.
Changes walkthrough 📝
results_test_k8s_autoscaling_deployment_count.md
Updated deployment count autoscaling test results..keda/results_test_k8s_autoscaling_deployment_count.md
results_test_k8s_autoscaling_deployment_count_in_chaos.md
Updated deployment count chaos test results..keda/results_test_k8s_autoscaling_deployment_count_in_chaos.md
results_test_k8s_autoscaling_deployment_count_with_node_max_sessions.md
Updated deployment count with node max sessions results..keda/results_test_k8s_autoscaling_deployment_count_with_node_max_sessions.md
results_test_k8s_autoscaling_job_count_strategy_default.md
Updated job count strategy default test results..keda/results_test_k8s_autoscaling_job_count_strategy_default.md
results_test_k8s_autoscaling_job_count_strategy_default_in_chaos.md
Updated job count strategy chaos test results..keda/results_test_k8s_autoscaling_job_count_strategy_default_in_chaos.md
results_test_k8s_autoscaling_job_count_strategy_default_with_node_max_sessions.md
Updated job count with node max sessions results..keda/results_test_k8s_autoscaling_job_count_strategy_default_with_node_max_sessions.md